I implemented solution #3 above for StatefulTreeCache, since normal usage of clustered SFSBs with nested beans will lead to ERRORs in the logs. I think the usage pattern that would lead problems with non-clustered beans is more of an edge case (requires the parent to hand out a ref to the child), so I won't implement it in SimpleStatefulCache without more feedback. The callbacks related to activation/passivation are also not handled correctly. See http://jira.jboss.com/jira/browse/EJBTHREE-849. The same analysis I applied in EJBTHREE-849 could also apply to the @PreDestroy callback. Currently, o.j.e.test.clusteredsession.ExtendedPersistenceContextUnitTestCase is failing because this callback is not invoked. I'm not sure if the spec requires invoking the @PreDestroy callback in this situation though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007303#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...