Reverse node reference only displaying if nodes were created together

I am not certain if this is a bug or if I've simply configured something incorrectly. In a nutshell, when I try to display reverse node references from multiple node ref fields, Views will grab a related node only if I created the current node "from" that node, and in that case, it displays that node for every node reference, regardless of what relationship I specify.

Ok, so, I've got two node types, A and B. A has a handful of noderef fields that all point to an unlimited number of B nodes (which can be referred to by several A nodes). Basically I'm trying to set up a many-to-many qualified relationship but got fed up with the Relation module.

What I'm aiming to do is to have the B node display view show A nodes that refer to that B node, either separated by which noderef field in the A node is making the reference, though just a list of all the A nodes that refer to the B node from any field would be ok too (I'm getting less picky as I struggle with this).

The way I have Views configured right now: I created a Relationship for each noderef field reverse. Then under Fields, I have a Node render for each Relationship.

However, what seems to be happening is that if the B node was first generated through the create interface for a specific node of type A (I'm using a select existing or add new widget for the noderef fields), that A node shows up for all of those fields even though only one should apply; and if I added an existing node B to a node A, or add a new node B to an existing node A, it doesn't seem to be recognized as related, and doesn't show up at all in my View. To restate, I'm only getting any a reverse reference to show up if both the A and B nodes in question were created at the same time.

Hopefully this makes sense. Please let me know if I can be more specific on any point. Any help is greatly appreciated! :)