tadeubas Sorry for the late answer. Yes indeed, if you need to only deactivate the rendering of your elements, a simple AABB check (of for better performance using a QuadTree) is perhaps enough.
Starling-Spatial-Deactivator has especially been designed to safely handle game objects deactivation when entities are interacting with each others (mostly when using a physics engine). For example if an entity is resting on another one, the supporting one should never be deactivate if the relying one is not.
But in any case, Starling-Spatial-Deactivator could be also suitable for you needs and can perhaps be even more optimized than a simple AABB check since objects are organized by chunks and AABB check only happens when chunks are activated or deactivated. So this means that internally, it won't do AABB check on all your objects at each frame but only when the active area moves (your camera) or when your objects move and therefore change some chunks activity.
I hope this may help if it's not to late đŸ˜… For further details about my approach, please check the article I wrote to present the advantages of it: http://adolio.ch/projects/Starling-Spatial-Deactivator