I still say some thought is needed. Here I trick the thread pool into instantiating more objects (and subsequently destroying them). So even the thread pool calls pre destroy. Question remains what to do with that 1 instance that stays in the thread pool on undeploy... deploy... | 12:34:16,108 INFO [StackedStatelessBean] post construct org.jboss.ejb3.test.wolfc.StackedStatelessBean@6258e1 | 12:34:16,109 INFO [StackedStatelessBean] 2 is invoking next one | 12:34:16,112 INFO [StackedStatelessBean] post construct org.jboss.ejb3.test.wolfc.StackedStatelessBean@fadb88 | 12:34:16,114 INFO [StackedStatelessBean] 1 is invoking next one | 12:34:16,114 INFO [StackedStatelessBean] post construct org.jboss.ejb3.test.wolfc.StackedStatelessBean@183aedf | 12:34:16,114 INFO [StackedStatelessBean] I'm done | 12:34:16,114 INFO [StackedStatelessBean] pre destroy org.jboss.ejb3.test.wolfc.StackedStatelessBean@fadb88 | 12:34:16,116 INFO [StackedStatelessBean] pre destroy org.jboss.ejb3.test.wolfc.StackedStatelessBean@6258e1 | undeploy... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963138#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...