Hi Chawn Reagan,
If you are referring to primitive members of the classes and not navigational ones then this is expected behavior. The object container is populated with all primitive members of the object. The point here is that if the fetch group contains a navigational property that points to another object (or collection), that object will be also fetched. It will not however filter on any primitive properties. You will always fetch them and have them in the container.
It is in fact possible to use fetch plans with the object container using the approach you have described, but only for specifying extra fields to be loaded, you always get the primitive members of the object.
I hope this helps.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items