"wolfc" wrote : | There are both patterns and anti-patterns to pooling. What I showed at JBW was a resource-starvation scenario which makes EJB 3 (/ pooling) behave better than MC (/ instance). The question is whether to incorporate something like that in MC, but that's not what this thread is about. :-) | OK then OFF-TOPIC Pooling has nothing to do with what you are talking about. Using a factory to create a new instance of stateless object without pooling rather than using a singleton also has the nice behaviour of not causing contention and not having to worry about thread safety etc. ON-TOPIC I agree, the factory should just be used to create objects for any pooling implementation ejb3 or the user cares to implement (including none :-). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136363#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...