If a conversation gets deactivated, the code which actually iterates the map of conversations in org.jboss.weld.context.AbstractConversationContext is erroneous and easily runs into a ConcurrentModificationException if there is more than one conversation. We consider this a pretty serious defect because its not possible to use JBoss AS 6.0 GA for a real-world application.

See attached patch for a fix.