1. http://labs.jboss.com/portal/jbossejb3 - JBoss supports standalone EJB3 access, useful for unit tests, remote clients, etc.
2. I'm not an authority on this particular use case, but from what I know, session persistence is clusterable. You can use JBossCache to store both to local disk and also on remote hosts.
Thanks genman, your help is greatly appreciated.
Answer to question 1 is great. I have actually picked up this book now. I think it will be a great resource to getting JBoss implemented for our application.
Regarding your answer to my second question, I am actually more concerned about deploying my app.war file. Tomcat supports hot deploy, but when that happens I lose my sessions with the client. I am trying to determine if JBoss allows me to deploy my app.war without the current users who have established sessions with my old app.war losing their session and being booted to the log in screen as if they have not been authenticated. Currently we have an authentication test on each page that validates that a user has been authenticated. This is stored in a session.
Any ideas anyone?