OK, so, forget *everything* you know from Spring, etc. :-) In Seam and EJB3, persistence context != transaction context. So you can have an SFSB with an EJB3 extended persistence context that spans multiple transactions. Or you can have a Seam conversation with a Seam-managed persistence context that spans multiple transactions. None of this is in any way related to JSF or to Seam transaction management. I strongly recommend against the idea of spanning an atomic JTA transaction across multiple calls to the server. Instead, use a conversation, and span the conversation across multiple calls. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021740#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...