For deploying multiple apps, you're better off with JBoss than with multiple Tomcat embeddeds. A single Seam app on JBoss might be able to run in that little memory.
But seriously... if this project has so little resources allocated to it that 96mb is all that can be spared ($3 worth of memory?) then you should be asking questions about the project itself.
I will not be deploying multiple WARs on a single server. I only intend to deploy one WAR that is the Seam application. What I meant was, as I deployed more pages and more beans than the Seam Hibernate hotel demo application, will resource becomes an issue then due to the stateful nature of Seam? Or is that plain irrelevant? I do not expect high traffic at all but sure if you deploy something on the Web that will be accessible to everyone.
I do not plan to use any EJB or other JavaEE-specific features so I am open to Tomcat standalone if that is more resource-friendly than a full JavaEE AS like JBoss.
I am on paid hosting with a VPS-based setup and cannot afford to go dedicated at this stage, because it is not commercial in nature. Sure if the Seam app is running on my desktop dedicated with 2GB RAM and Core-2-Duo I will not be too much concerned about this.