Sorry to say it has not been fixed.
The problem only occurs when the child's FK is also its PK, but making a modification to the schema likely has other undesirable effects, like the EDM not allowing the relationship.
Although it won't help now, the problem has now morphed slightly. The error now occurs only when the PendingEntity is not found (it doesn't exist in the DB), so what you'd now see is bindings sometimes working and sometimes not, depending on the data.
Unfortunately a bug report was never opened for your earlier query about this issue, but I've opened one now and we will have the problem fixed in one of the 6.0.7 EAP drops.