Ryan,
From Bjorn's answer and reading about the functionality in the new javascript API, it appears to be on the horizon. For the time being, I am creating an empty cached service that goes down to whatever minimum scale I want it to be. So if using the google/bing/arcgis scale, it goes something like
[...]
1128.49722 (standard minimum scale)
564.24861
282.124305
141.062153
70.531077
I serve this up, but I don't actually create the cache but rather I double host all my other cached services. Maintaining the cache to 1128.49722, then having a dynamic service that is visible starting at 1128. It is slower than cached services, but at least you're able to view something and not have to take up all the memory at the lower scales. Have a look at my site centerline, parcels, and 2014 aerials are cached to 1128, and then dynamic after that.
https://gis.miottawa.org/ottawa/geocortex/propertymapping
(I think this one is only necessary to go to 282)