It never ends!

OK, so I hit similar problems even in WCF! There is no mercy! Using a WCF service it simply doesn't like lazy loading. So it looks like I'm going another approach that a number of people recommended. Keep the relationships on the objects and then create calls that can be made asynchronously to populate them. If I try and bypass the WCF service then I need to use the wrapper classes because WPF/Silverlight won't support the domain objects directly, so at the end of day, I save more time by rewriting my domain objects than I do cutting out WCF. I guess that even though I threw away my Silverlight application this puts me on track to make one again in the future :). New technologies sure have a way of making life fun.