Hello Forum, I have run into this problem again with nested conversations and wonder if anyone has see it in the interim. Using @End(beforeRedirect=true) does not help me this time. The symptoms are identical to my prior posting: when I @End the nested conversation, Seam destroys one of the components in the parent conversation. The destroyed object is annotated like so: @Stateful @Synchronized @Scope(CONVERSATION) @Name("profileMapperMgmt") @Conversational @LoggedIn I print the conversation id in the @Create and @Destroy methods and see: Client: [profileMapperMgmt] (8) Create ... ... Client: [AsciiEventEditorBean] (9) Create ... ... Client: [AsciiEventEditorBean] (9) Destroy Client: [profileMapperMgmt] (9) Destroy ... In this example, profileMapperMgmt is destroyed in conversation (9), the nested conversation, when it is ended. There are no references from the nested conversation's components to this particular object. Nor is the object used on the page (facelet) that is rendered by the components in the nested conversation. This just seems like a bug to me. The docs say the parent conversation's objects are read-only when in a nested conversation. Has anyone else run into this problem or anything similar? Thanks PdP View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095837#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...