I'm having some fun writing a strategy/fantasy game with Seam.
Unlike a typical Seam application there is a lot of asynchronous activity; scheduled methods update player data, both offline and online, and using Icefaces' Ajax push the players views are updated with relevant information, like available gold, stone, chat messages etc.
My problem is the conversation scoped seam managed EntityManager is more of a hindrance than a help; dealing with all the detached entities is a chore and constantly flushing to sync up the EntityManagers is hurting performance.
I've considered putting the EntityManager on application scope, but I fear that might cause performance and/or memory issues. Alternatively I'm wondering if using a separate entityManager for frequently changed data will help performance.
Any ideas?