[ http://jira.jboss.com/jira/browse/JBSEAM-1844?page=comments#action_12420501 ] Jesse Sweetland commented on JBSEAM-1844: ----------------------------------------- I am having a similar issue. In my case, I have two SFSBs. A method is invoked on the first, which outjects an object that is injected into the second, and starts a nested conversation. A method on the second raises an event using Events.instance().raiseEvent, with an argument, which is then picked up by a method on the first SFSB that is annotated with @Observer. After the @Observer method fires, the first SFSB component is cleared from the conversation context. By that I mean when I go to debug.seam the first SFSB component is initially listed in the conversation context, but when I click on it the page refreshes and instead of seeing the details of that bean I see all of the conversations and scopes and the first SFSB component is no longer listed. Neither the @Destroy nor the @Remove method is ever invoked. Both beans are in conversation scope. Setting create=false on the @Observer annotation does not have any effect. Putting the first bean in session scope resolves the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira