If lone wolf programmers can add features without review, then you have the possibility to save some serious money by firing everyone in your configuration control team. Seriously, there is no point to doing configuration management if you're not going to manage the configuration.
And while they are at it, they can save money by canning that developers management. Apparently that manager feels that it is OK for programmers to devote time to coding and installing whatever they feel like. Most companies are under the illusion that the company and the customer choose what will be deployed. But apparently this particular programmer's whim is more important than the priority of features chosen by the system owner/product owner. SO we can pink slip the product owner.
And if people can bypass your QA team, why pay them?
Objectively speaking, he is not a good developer - he is a rogue developer with no respect for his team, his management, or the long term health and welfare of the product. If he were my programmer, I'd call him into the office and shut the door an explain that either he works on the team, with the team and for the team, or he doesn't work on the team. - I'm happy to provide him the number of the unemployment office with his termination for cause letter and the legal paperwork that the company is preparing to file against the damage done to reputation.
Of course, I'm a jerk; most people would probably take a more constructive approach. I was trying to convey that this is largely tongue in cheek; this is not a constructive approach and will not solve the problem. I do think that the employee needs to understand the full implications of these actions, but this is not realistic or constructive.