I just realized that this works for at least the create and delete operations, but not for the read. Using a 1-to-1 multiplicity here generates the following error when trying to navigate to the URI of the child resources: "Multiple resources found. Inconsistency between data model and service description found."
I may be wrong, but it seems like two services are necessary for entities with parent/child associations: one for create, update, delete operations and the other for read?