Yup, that's a bug. The proper fix is to unbind the various JNDI entries on destroy(), but I'm concerned that some services in the app server rely implicitly on the bindings provided by the transaction manager without actually declaring a dependency on it. I have a feeling these will break if I use unbind(). Maybe we just bite the bullet, make the change and clean up the dependencies as needed. Or we could wimp out and use rebind() instead of bind() at create time, which would allow for clean service restart whilst being less disruptive. Any thoughts from the AS side of the house? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200100#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...