It's good that it works.
Yes, it would be ideal to not have to ship such a big JAR but that's the implementation decision that was made. The same generated JAR is used for carrying the stubs and also all files needed to launch a Java EE app client using the appclient command or using Java Web Start. Granted, you don't need all that other baggage to access the stubs, but the other uses of the JAR need all that content.
Looks like It's a doc bug (or a code bug, depending on one's outlook) that get-client-stubs is described as creating the stubs if they weren't generated during deployment.
- Tim
[Message sent by forum member 'tjquinn']
http://forums.java.net/jive/thread.jspa?messageID=470548