I don't know of a list of required JAR files. I think you will have to start with a minimum configuration and add more jars after each "ClassNotFoundException". This way, "jboss-all-client.jar" is not required, because it does not contain any code.
Maybe Tattletale will help to resolve the dependencies:
If you have a minimal list, you might add a JBoss wiki entry.
thank you for the suggestions. The idea with the minimal list is good but not really realizable, because there are too many interdependencies between the JAR-files. Thus I have decided to deploy the application with all required JAR-files from the jbossall-client. Now my clients work, but I think, it's not a practically deployment-solution from JBoss to handle with so much JAR-files.
the list of required JARs depends on your app. The more JBoss features (EJB2, EJB3, EJB3 injection, Web service access) it uses, the more libraries it needs. So it probably is quite hard to define a set of minimum required JARs, and it might change with each JBoss version.