eager loading (as configurable with FetchPlans) allows for fetching related entities in a more efficient way than lazy loading. Nevertheless, all access to the related entites is still tracked, and can lead to a server fetch operation when the needed data is not present or outdated. If the data already fetched is available on the client, it is used and the accessed reference or collection object is just created in memory.
This means, there is no explicit loading of related entities call, as all accesses are tracked, and you just need to follow the reference or collection properties.
the Telerik team
Q3'12 SP1 of OpenAccess ORM packs Multi-Table Entities mapping support. Check it out.