Does it also happen if your ScopeType is "conversation"?
The event context only spans a request, you need a long running conversation. Take a look at the reference manual for a full explanation of the Seam scopes.
Yes, I changed the Scope to CONVERSATION, but omit the @Begin and @END tags. The page get's loaded (calling the Create method) and then submit the page again (persist). Then the conversation is ended.
Are there any recommendations about how to use the Scope. I am asking because stick the bean to the session context compared to the conversation should result in less resources (Memory). Or is there some more overhead to take into account?
If you use a temporary conversation (no @Begin/@End) then you will get a new bean created for each request (like event). A conversation scope should use less memory than a session scoped bean as a conversation is normally shorter than a session.