I was forwarded to this post from my own post on the issue. Instead of re-posting my entire post, I'll just hit the highlights here: 1) Glad Bungie is finally hitting one of the more requested issues, however I do have a few problems with the update. 2) The whole "memory limits" thing Bungie is telling us is complete bull, unless they've absolutely failed in creating their C++ container classes, which should clean up memory when it's not being used. 3) Hitting on #2, there should have been no reason why they couldn't then use the highly requested multiple pages of vault space feature. Since the inventory is downloaded from the server you simply load up what you need, when you need it and free the old memory upon completion, and voila that memory restriction is no longer existent. The big thing from my post though was if Bungie was going to hold onto the notion there, then a solution that could work perfectly fine would be to create an [b]Online Vault[/b], one that you could not access from in-game, but use B.Net or the app to transfer items to & from, and since this would only be dependant on the server storage of a few KB, could easily be about 10 to 50 times the current vault size.