I tried to reproduce this here. It seems, that the exception is caused by an unexpected state of a collection or map field. In order to fix this, we would like to know the structure of your entity and what kind of operations you did on the entity in the context; also, are there fetchplans involved?
OpenAccess ORM Q3 2013 simplifies your model operations even further providing you with greater flexibility. Check out the list of new features
shipped with our latest release!