managing multiple relationships with the same membership-constant-URI

I’m attempting to manage a relationship and its inverse on an LDP server, and started by using a using a direct container that has triples for both ldp:hasMemberRelation and ldp:isMemberOfRelation.  The LDP implementation I’m working with allows this, and some unofficial sources on the internet also support this practice.  Upon reading the spec, however, it seems that this not the way to go.

Section 5.4.1.4 States:

Each LDP Direct Container representation MUST contain exactly one triple whose subject is the LDPC URI, and whose predicate is either ldp:hasMemberRelation or ldp:isMemberOfRelation. The object of the triple is constrained by other sections, such as ldp:hasMemberRelation or ldp:isMemberOfRelation, based on the membership triple pattern used by the container.

Given the conflicting information I’m reading, and what the software I’m working with allows me to do, I’m confused as how to proceed.  What is the best practice for managing multiple relationships with the same membership-constant-URI?  Should I maintain a separate container per relationship?

If so, I assume I should report this back to the maintainers of the LDP server I’m using?

Any help is greatly appreciated.

~Danny