As a rule, it's generally not a bad thing to learn about a technology even if it's going to change drastically. It's nice to have a point of reference about these kinds of things.
I've been using WCF in .NET 4.0 and I can tell you that not much has changed. There are a number of under-the-hood changes that won't affect you, but here's a few of the things that you might keep in mind as you are learning that are going to change:
- Configuration has been simplified a
bit (but in my experience, not that
much).
- ReceiveContext that will make
transactional receives from things
like MSMQ easier (if you do this, you
know why this is important).
- Big improvements to support RESTful
services and how DataContracts work
in the context of an HTTPRequest.
- WS-Discovery support (read more
here)
- A Routing Service for doing
routing/multicasting of messages
- Support for the new Windows Workflow
Foundation bits (they completely
re-wrote WF)
- Tracing now uses native ETW, so
should be faster. (This is a great change).
That's it. The programming model is left relatively untouched. The configuration looks to be 99% backwards compatible. Learning now won't hurt you later here - only give you a better foundation for when 4.0 does arrive.
You can read a little more here (most of my points are from here): http://www.aspnetpro.com/articles/2009/04/asp200904mb_f/asp200904mb_f.asp