thanks a lot Pete, if you think it's a bug of the tools then all the rest of my confusion doesn't apply. Still you say anonymous wrote : Seam doesn't call the @Remove, the EJB container does That makes some confusion, I would say that the EJB containers calls the destroy, and not the remove: as you write later on anonymous wrote : No, Seam doesn't call methods @Remove, you do . Still, isn't documentation wrong when it says anonymous wrote : In Seam, all stateful session beans must define a method with no parameters marked @Remove. This method will be called when Seam destroys the session context.? Why should Seam need a @Remove method? How does it identify the correct method when multiple methods are annotated? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118269#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...