I think you can select a few hundred transactions to send to a consolidation address before you reach that size though.
This is getting rather frustrating. It worked for a few of the addresses that I had a small amount in, but now that I'm trying to move 7875.754885 bits it just gives me the error that it failed to create the transaction. I've tried reducing the amount I'm trying to send from that address, to less than 1000 bits and I STILL get the error. If an address has a large amount of bits in it I can't seem to get it to send from that address. This is really baffling.
OK thanks to a friendly fellow user, I was able to figure out that I had a ton of small inputs and needed to check them off individually until I hit the byte limit. Kind of a pain but it works. Part of my reason for doing this in the first place though, is this: I created separate addresses for specific purposes, such as an address for exchange purchases, and multipool earnings. The idea was to be able to easily see how much I bought over time, or earned through the multipool. But I'm finding that as the Bitstar client mines new coins it seems to use all of the addresses I've created which defeats the purpose. Is there some way to constrict the address used for mining?
Not unless you no longer want to stake, POS uses coins to create coins therefore will always turn large inputs into smaller ones, but if you "house tidy" every 1-2 weeks you can keep it from getting too bad. This is just how POS works.