The memory issue has been resolved in the CVS HEAD version in case you whish to re-evalute.
since it seems that there are a couple of Beta-2 issues fixed in CVS, could anyone give me a hint when Beta-3 could come out? Thanks in advance.
The inefficient CPU usage is I believe a limitation of most java VM implementations. Each thread is still running inside a single process so often doesn't take advantage of multiple CPUs. The usual workaround for this is to run multiple instances of the program in different VMs. For this to work a program must be designed to expect this kind of rollout. For instance any data access must be designed to cope with other processes modifying it's data. File access/Memory caching etc is suspect in this situation. A transactional data source such as JDBC must be used to avoid corruption. I think JBoss EJB container is designed to allow this without problem. I am not sure about the JBossMQ service. Can this be done? Try it and see.