Well for one... a stack overflow.Originally Posted by King Mir
...and secondly, more often then not, most of those objects will be sitting idly when they don't need to be there at all. When you write more complex programs, you have to manage your memory and keep only what you need. You could keep static objects for all the rendering information for every map you make, but what's the point if you only render one map at a time.
I remember one of the first real programs I wrote was a trivia program. It have several games each with 10 questions. I decided to hard code all of the questions into strings, which totaled to about 400 strings between the questions and multiple choice answers. I only needed maybe 50 strings in memory at any given game. Not saying this is a prime example, but even when you get better at programming, there could still be bad memory management.