That's not WinFX (it's not WCF+WPF+WWF at all). That's part of WinFX. WinFX is the new Microsoft API and as such it's the go to card for general future development. The .NET FX is considered part of the WinFX model as well. This is why, when I teach .NET, I never say ".NET" I always refer to managed code as "WinFX" because I'm teaching the API in general even though nothing in my WinFX course has ANYTHING to do with WCF, WPF, or WWF. It's still WinFX.
That said, WinfX is different things to different people. For instance to a marketing person WinFX might be WCF, WPF, WWF, but to the architects and developers it's the new world of development. Not a technical idea, or anything like that, but a new model, a new mindset, and a fully new API for development and architecture.