Carlo: Bean Provider == Application Developer. The APp developer is responsible for closing connections. Also, i see nothing in the spec that supports your claims. 4.2.1 says that the container is allowed to use ObjectStreamClass techniques for injected things, which is what we do. Furthermore, constructor invocations don't even happen in Java serialization. How EJB3.0 works now is basically the same on how it worked in our old container. The problem with the idea of reinjection, is that there may be state associated with the previous injected reference. I.E. Extended persistence contexts, SFSB references. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016473#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...