i would expect it to give "" (empty text) since that's what's given when trying to get an object that doesn't exist with the OBJECT block, and because 0 just isn't a very useful result.
0 seems to come from uninitialized variables
Snap! doesn't have a NULL thingy type so just has to wing it with supplying "" or 0 or an empty list
As long as it's consistent, it's usually not a real problem
i'm well aware of that
what it uses does not make sense in this context and doesn't match other similar situations
Lets call it an unexpected result then and not a bug 
there isn't an "unexpected result" category on the forums