The problem with extremely long-running conversations in Seam is that Seam-managed persistence contexts are bound to the conversation, and will fill up with stale data. It is *possible* to futz with stuff to get a PC-per-nested-conversation, but it wouldn't be that transparent. If you're not using Seam-managed PCs, what you are doing would be OK. A possible solution is to have "per-action" state in a per-nested-conversation SFSB, with an extended persistence context bound to the SFSB. ie. @PersistenceContext(type=EXTENDED) Actually I think that's a good way to do it :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060972#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...