"bstansberry(a)jboss.com" wrote : "pete.muir(a)jboss.org" wrote : (which leads to the SFSB's remove method being called unless you explicitly ask it not to). | | How do you "explicitly ask it not to"? The timing of this work is being driven by a support case where the customer is having issues because of the sessionDestroyed call. If there's a workaround, that would be great. You can annotate separate methods @Destroys and @Removes on your SFSB - this will lead to the remove method not being called when the component is destroyed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177020#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...