Ive been having a wierd problem with a COM+ component in VB.NET. My component has tranaction required, object pooling, and construction enabled. I instantiate the object which in turn fires the "New" event in the class which does some initialization tasks and sets some module-level variables. When I call a method in the class, the second the method finishes, the "Finalize" event fires and closes down my object. If I call the method again, it fires the class's "New" event again, then finalize again, and so on.. Every method call that completes a transaction - either explicitly or automatically - destroys and recreates the object thereby giving me poor performance if I call more than one method at a time while that class is instantiated. Has anyone else had this problem?