Sorry for my bad english..
What you are trying to do is not fully supported. Well, at least according to the last doco I read.
There is an annotation @PerNestedConversation that can be used to allow nested conversations to contain individual instances of Seam beans. However, according to the java doc on the class it is not recommended that applications use this feature.
In otherwords. In this scenario you are going to have to not create a nested conversation, but rather create a brand new conversation and do your work in there. Unfortunately the out of box features of Seam do not really work well for applications that have this scenario.
I spent a fair bit of time experimenting with various navigation models for Seam apps. All of which have some serious draw backs.
If you are only just getting started on the navigation stuff I would recommend building your own navigation framework to make this side of things a lot easier to build and maintain.
If you would like to see how I've done this I have written a fairly long explanation in this thread here. http://www.seamframework.org/Community/CrazyIdeaProgrammaticNavigationStaticOrDynamic
And I'm following up a current issue with my design on this thread http://www.seamframework.org/Community/EndingNestedNaturalConversations
One day I really really should actually write my own thread for this instead of tagging onto the end of other people's :P