I'm afraid I can't offer you any easy solution to your issues, all I can offer is that not all iPhone 5's are as bad at battery life as yours seems to be. I got a 64GB (black if that matters) iPhone 5 from an AT&T store near Indianapolis, IN on launch day (21 Sept). I couldn't pre-order, so I took my chances and got lucky getting a phone at an AT&T store (the local Apple stores had already sold out).
I regularly get 18+ hours from when i unplug in the morning until I plug it back in at night. Most days, I use the phone such that it reports about 4-5 hours of usage and I have somewhere around 15-30% battery remaining. So far today, it is reporting about 3 hours since I unplugged it, about an hour of that as "usage" and it is claiming I have about 92% remaining.
I haven't really disabed anything on the iPhone other than bluetooth, but that is because I don't like my iPhone broadcasting itself as being there when I don't use that feature. I left LTE on even though I am out of LTE service more than I am in it. When I am at work, I have poor AT&T coverage in general, but I have good wifi coverage. When I am at home, I have decent "4G" coverage, and good wifi. WHen I am a few miles from home, I can get LTE coverage, so I leave it on to take advantage of it when I can get it.
I don't know if the problem for you is hardware, or that you just happen to have the "perfect combination" of apps which exposes a software bug that is causing the battery drain for you. Since people are reporting this issue with iPhones restored as "new" and no additional apps loaded, that implies that this is not a software issue, so is it a batch of bad components, or possibly a procedural issue on one assembly line for a while, or is it just a failed single component i your iPhone? It is hard to tell, but since iPhone replacements from Apple under warranty are generally refurbished iPhones returned by other users, the chances of you getting a replacement that someone else returned for the same reason are probably higher than the odds of you getting a new one with the same issue...