ASP.NET Technique Headcheck

[Dave Swersky]

I've written a hierarchical API using VB.NET. This API forms the
foundation of two ASP.NET applications and an ASP.NET administration
application. The API abstracts commercial property management.

A "management" class can instantiate the top-level object, Property, and
each downlevel object can instantiate its own children using a method or
provide them from a collection-type property. Here's the hierarchy:

ManagementClass > Property > Building > Tenant

Here's my question:
My current plan is to pop an instance of the management class into
Application state and use it to instantiate downlevel objects.

Can anyone see any serious scalability issues here?

TIA!!

Dave Swersky
(e-mail address removed)