According to this outstanding bug here, failing to put an access strategy on a collection that doesn't have a setter result in an exception that is enigmatic at best. Thankfully, I found this and found a mapping that didn't have a default access strategy on it...that fixed it.