I dont think that it is right. Stateful session bean cannot be pooled becauase the Class.newInstance method on the bean class must be called when the client calls the create method.
Please have a look at the life cycle of SFSB.
when client class create() the following steps are executed
Also from the spec -
The container�s caching algorithm may decide that the bean instance should be evicted from
memory (this could be done at the end of each method, or by using an LRU policy).
It is clear that the bean will be removed from the memory => no pooling.
Originally posted by Vinod Jon:
My answers may not be correct but to my knowledge,
1) Some (or most) app servers pool stateful session beans by seperating the state information from the bean reference, during passivation.