Symbol table is annoying. Nothing like having the program working right with the cartridge but then running out of symbol table space when you add the runtime. There are work arounds of course you are really talking a large program with a lot of variables before you even hit the wall. If you know in advance you are going to have a problem it isn't that tough to reuse your variables and edit your RT to only routines you use. IMO this is pretty much standard programming practice too. Just declare your loop counters as global variables and treat them accordingly. You seldom have need for more then a couple of 8 bit and 16 bit volatile values anyway.
I work with a lot of 3rd party global symbols in Action! when I am creating applications that run in the BBS Express Pro! environment. Therefore, it's not uncommon to run out of global symbol table space. Yes, it's possible to further split up programs and cull runtime symbols, but as you say, it's annoying (because it slows down the software development process). I'd love to see an Action! upgrade that includes larger symbol tables by default.