Then there's nothing to configure. You are not deploying any EJB's, so none of JBoss's EJB container stuff will be used. Of course you probably don't want to be using a full J2EE application server just a s a Web Container.
If starting an out-of-the-box instance of JBoss take more than about 25 seconds, I'd consider getting more resources for the machine you are developing on. Just for comparison, the 1GB RAM, 3GHz processor machine I'm working on at the moment JBoss 3.2 starts in 11 seconds. Curiously, staring Tomcat stand alone takes about the same time.
The easy way JBoss registers stuff for deployment means its also easy to remove services from the app. There's stuff like this the jmx-console, jms clustering services etc. are all non-essential. There's also things like the default hsqldb data source which you don't need. You can just play around, trial and error to see what you don't need.