Then again, neither can VB COM components due to "no thread affinity".
VB also can only create apartment-model components and therefore, VB components cannot be pooled. I think for the time being, only VC++ component objects can be pooled. I don't know about Java though.

>I should have added that VFP COM components cannot play in the COM+ pool because they of their apartment model multithreading.
>
>
>Quoted from "Requirements for Pooling" in "Object Pooling" in Jan 2000 MSDN:
>
>"No thread affinity
>Poolable objects cannot be bound to a particular thread, otherwise performance could suffer. For this reason, poolable objects cannot be marked Apartment model; they must run in the Multi-Threaded Apartment or the Neutral Apartment. In addition, poolable objects should not use thread local storage (TLS), nor should they aggregate the Free-Threaded Marshaller (FTM)....."