We really can't prevent anyone from copying a design. It might not be the ethical thing to do, but there no real way of stopping someone if that's their goal. However I still wouldn't shame them. I would call them out in a more gracious manner. Something like a list of those companies and title it "Copying is the sincerest form of flattery" or along the same line.
Why not use them to your advantage, use them as marketing tool and if they refuse then force them to remove the design. Maybe only then, at that point it is ok to call them out and shame them.
Shaming someone just created an adversarial effect and it brings some negative publicity too. If you can show that you are gracious and is able to manage and find a middle ground in such a situation, it'll show a better you. I rather work with a company that I can always negotiate with than one who always take the hard line.
This method does not convey any understanding of the problem. I'm not sure it's a good idea in the long run. It'll create a class of people who know how to solve a particular mathematical problem, but don't understand why.
Solving a problem is the easiest to learn and retain that knowledge. Get an account in development EC2 which I think is free, or something cheap in the cloud like prgmr.com and build a linux server and learn. Deploy your application manually and solve all the issues you face. Linux is so wide spread these days, there are very little that you can't an answer on the web.
I say CentOS or Ubuntu (w/out UI) is a good way to start. Those 2 distributions have many step by step solutions scattered on the web such as stackoveflow and forums posts. Slackware, Arch Linux or Gentoo are great for their target audience. IMHO they provides very little out of box for a noob and it's very easy to get lost in what you can set, break and/or fix. There is nothing more demoralizing that spending 2 days digging around the web for a problem that has numerous answers and you've no idea what everyone is on about.
Books are very useful guidelines, but getting your hands dirty is how you'll really learn.
I'd suggest avoiding prgmr (who I think are awesome by the way) and opting for somewhere like Linode, just because it makes it so easy to wipe your VPS with a clean image and start again. (I'm talking specific to this thread, not as advice for everyone.)
For me that is a very helpful feature. I've done installation many times and I've done them to a cheap machine at home so I'm quite familiar with the process. It's the ins and outs of the linux that I was not able to get for a long time. Being able to wipe a VPS with a clean image allows me to quickly start over when I have mess things up so bad.
The only thing strategic about "realigning workforce" and outsourcing your former core development team is to slowly wind the company down to a shell and then make the financial numbers look good on paper.
This way the CEO and board of directors can give themselves huge bonuses for "saving" the company. Then 5-8 years down the road, when no more can be squeezed out of the Nokia brand name, they will look for a merger as the next strategic move.