1) You don't need to call @Remove, since Seam will call the @Destroy method, which removes the bean, at the end of the conversation. The reason for @Destroy @Remove is to make sure that the conversation can't possibly be destroyed without the SFSB being removed. 2) No, it is definitely not required. There is nothing wrong with having a bunch of stateless actions all using the same conversation-scope persistence context. This is part of the magic of Seam - components with different scopes can all work smoothly together in a loosley coupled way, with no need for orchestration by the Java code. 3) If you are trying to use a Seam-managed persistence context, do *not* use @PersistenceContext, use @In instead. 4) Try using exceptions.xml: http://docs.jboss.com/seam/1.1GA/reference/en/html/events.html#d0e3695 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994111#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...