My project is split up into a typical 3 layer structure for a Silverlight app. That is:
I did something similar on a small project by creating a "communication layer" dll, which contained only the objects being passed between client and server. A variation of this (share a dll between all the projects needing these objects) should work for you. Watch out for versioning issues, though. Unless you have full control of both ends, an upgrade to one end could cause headaches, if you're not careful.