this scope should be similar to the conversation scope of orchestra.
if no @ConversationGroup(MyGroup.class) is provided, the class of the bean is used as group.
it should be allowed to use different conversations at the same time (one conversation for 1-n beans).
it should be possible to invalidate and/or restart conversations immediately (not at the end of a request) and it should be independent of plain cdi-conversations. so users can use both concepts in parallel.
it should be possible to create stereotypes.
if a meta-annotation and the bean don't host a group, the class of the stereotype is used as conversation group.