This question is pretty old, but probably still relevant. I, too, like the Conversation scope. However, I never chain them. I tend to have pages backed by a SessionScoped bean that will present a general list of some type of thing, say Quotes, and then if the user chooses to edit or create a new Quote, then I go to a ConversationScoped bean to handle that detail. This allows the user to choose to open multiple Quotes in separate tabs, where each will get their own Conversation, without going crazy trying to remember which tab went with which other tab. It also works well if a quote is opened from an external link, such as one embedded in an e-mail notification or originated by a desktop application, where the new page will get its own ConversationScoped bean and not interfere with any other tabs already open in the same session.