maybe things are not what you think they are. You can inject the Conversation component and add logging functions to the method. Check if it is really a nested conversation. If you try to nest from a non-long running convesation Seam will change to a
The application is in production or development mode? If in dev mode, you may check the scope of EntityHome in Seam debug page (whether it is in root conversation or nested conversation).
The solution for my problem is the annotation @PerNestedConversation, which isn't fully tested.