I hate to say it but first that sounds highly too stubborn that I wanna say it sounds incompetent. Secondly there's still room to rename and if they want it to go anywhere sooner is bettee than later. Call is Weasel for all anyone cares (yeah I know IceWeasel... But still better than flat out WAMP). The worse part is some people might completely dislike WAMP altogether given some Unix only devs out there and might never see this due to poor naming.
This is true, and I believe sometimes developers should yield certain decisions to somebody else, or be willing to take useful advise (and act upon it after really considering it), you could really go from very good to exceptional if you can get over the hump of "but I already named it a thing", or whatever mental roadblock. As well as you don't have to change your code (reasonable reason not to 'change names'), it can be called 'WAMP' under the hood, but market it as something else, it is the 'WAMP' core if anything, but also clarify that it's nothing to do with Windows, Apache, MySQL or PHP (unless it's related to any of those). At this point if he called it the 'WAM Protocol' it might be a little better.