And secondly, that would result in the GPL no longer being complaint with the Open Source Definition[1], which does not allow "field of endeavour" restrictions. Whether or not the FSF cares about that point is questionable (I doubt they care much) but it could make life more difficult for F/OSS developers in general.
[1]: http://oreilly.com/catalog/opensources/book/perens.html
It's even worse than trying to force a teenager to tidy their room!
With all that said, I don't think it applies to licenses at all. Licenses are paperwork. Do I need to say more?
Sure, most weapons of war are created by companies which act within the law in order to do so.
A broader question is: I don't think you can revise the GPL, can you? If you change the GPL it's no longer the GPL referred to by the GPL when the GPL says that anything produced with the GPL must be licensed under the GPL, thus all existing GPL software will still be under the old GPL not the new GPL.
You'd have to start from scratch with a new licence and develop a new codebase.
I don't think that would accomplish much except hurt the DOD and hurt open source software that various parts of the DOD contribute to.
But even assuming the bad guys would abide by it - it gets tricky:
Does the police count? What about SWAT teams, what about the FBA, the CIA?
Is the coastguard part of the Navy in your country? Does that make SAR "military"? Could they use it only on rescue missions but not on law enforcement?