Restricting Object Entry causes Sim is Full

Today I turned off the "Object Entry: All Residents" option in my sandbox sim. I quickly discovered that people in the sandbox could no longer rez large (200 prim +) objects. The most complex object I have is a 300 prim canon - here's what happened when I tried to rez it in the sandbox. Note I was WELL INSIDE the parcel-- I was NOT trying to move the object, simply rez it next to where I stood. Re-enabling the Object Entry for All Residents immediately resolved the issue. I've filed a bug report but thought I'd post here as an FYI to help anyone who has a similar error/problem to diagnose it.

Can't move object to
{ 131.583, 111.387, 21.3764 } in region FurNation Omega because the parcel does not allow objects to enter from other parcels.

Second Life: Objects in FurNation Omega are unable to be created because the parcels they are being created on are full. Notifications from this region are temporarily deactivated.

Second Life: Your object 'Artillery Support 3.0' has been returned to your inventory lost and found folder from parcel 'FurNation Worlds - Omega Sim - Public Area' at FurNation Omega -1.76023, -0.511093 because it went off-world.

I bug reported a similar bug with this here, the function seems to be almost entirely worthless at the moment, as it just breaks too many things to warrant keeping it on

Makes sense. Looking at the sequence of messages, it appears that being sent to limbo is a by product of the restricted object entry setting. Note that in my example the return was because the item 'went off world'

Actually no, the limbo bug has been around for a while, it seems to have got worse recently, mb one or two updates back, but it's been around longer I'm told (I only noticed recently myself though). I posted my thread with that being the main point really since it's what's causing my trouble.
It was happening to me on a parcel without object blocking enabled, and will still happen on parcels where object-blocking is disabled after encountering this bug. It looks strangely like objects are moving <0.0, 0.0, 0.0> at times, in the cases I've noticed always when you sit on an object. In your case it is possible that it could be rezzing your object at <0.0, 0.0, 0.0> then MOVING it to the location you chose to rez it at, thus causing it to enter the parcel erroneously.
That would explain why it happens in both cases perhaps? It could even be the cause of the famous prim-drift bug, if objects are moving to <0.0, 0.0, 0.0> for whatever reason then 'resetting' to their correct location.