If your only sending objects one-way, you probably don't need to weave the client, the weaved fields will just disappear on the client. If you are sending objects both ways, then the weaving is required so the server know the difference between a field being null vs not instantiated.
If you include your persistence unit and eclipselink on the client (with meta-inf persistence.xml) then dynamic weaving should work on the client too. You may need a special or dummy persistence.xml that does not connect to the database.
Trying to weave one class at a time is probably a bad idea, as classes reference other classes, and you have to weave the class before it is loaded, otherwise it is too late.
Here is the JavaDoc for the static weaver,
and source code,