Yeah, Apple definitely doesn't like copyleft. That's okay; lots of people don't (especially larger companies – how many large companies actively release GPLd software?). It's a legitimate business decision, and there are some good arguments that support it (which you may or may not agree with).
The idea that organisations 'owe' the community copyleft software is therefore a bit foreign to me.
Furthermore:
We'll likely see pieces of Swift 2.0 thrown over the wall. But the best stuff will be kept proprietary.
That's a bit of a weird assumption. Apple's statement was the the Swift code and standard library would be open-sourced. What is the 'best stuff' that we're not going to get?
Apple's not-yet-executed move to liberate some of the Swift 2.0 code seems a tactical stunt to win over developers who currently prefer the relatively more open nature of the Android/Linux platform … the copyleft license of Linux itself provides the opportunity to keep the core operating system of Android liberated.
That's a bit flaccid. Google and the Android platform has equally went out of the way to isolate the platform from the effects of the GPL. In fact, I'm pretty sure one of the reasons Bionic (the Android libc) exists is specifically to limit the impact of GPL code on the platform. Android's use of Linux is basically a historical accident, and painting it as some kind of concerted effort towards software freedom isn't a compelling point.
TL;DR - you need to relax. Apple releasing open-source code is a good thing. We can now all benefit from using this code. Maybe you'd prefer if it were copylefted, but it's not – it's still good, and painting it as an evil move against software freedom seems like a bit of a mental stretch.