First, maybe exploded directories would help you. See http://wiki.jboss.org/wiki/Wiki.jsp?page=ExplodedDeployment. Since the war is a directory tree rather than a file, it is easy to replace or add files without restarting the whole app.
The other possibility is to add new directories to the main deployment scanner. You can do this via the "URLs" attribute on the jboss.deployment:type=DeploymentScanner,flavor=URL MBean defined at the end of server/xxx/conf/jboss-service.xml file.
Thanks PeterJ for the reply. I have tried the URLs attribute approach unsucessfully. It seems like it thinks that my war is corrupted or something. I get an error about the ZipFile being incorrect or unable to unzip the file or something like that.
However, the ExplodedDeployments approach seems to be working good. I have some more testing to do but that looks like the approach that we will go with.
Thanks again for the assistance.
Zip file corruption errors typically happen if the hot deployer attempts to deploy the war file before it is completely copied to the deploy directory (or the directory you added to the URLs attribute). To avoid zip file-related errors, you should copy your war file to a temporary location on the same disk partition as the target directory (deploy, or one specified by URLs), and then move the file to the deploy directory.
But as you noted, exploded directories are really the way to go for what you want to do.