Here are a couple of examples of dependency injection in the framework:
WCF's ChannelDispatcher has constructor injection (mandatory dependency) of IChannelListener. In general though, WCF relies on configuration to do user-level injection of optional dependencies.
System.Xml does poor-man's dependency injection in a number of places. For example, XmlDocument has a constructor injection (internal) on XmlImplementation. The default constructor just instantiates the needed XmlImplementation. XmlImplementation itself depends on XmlNameTable. XmlResolvers are another example of injection.
MEF's CompositionContainer optionally depends on a ComposablePartCatalog and ExportProviders. ImportEngine has constructor injection of ExportProvider
ASP.NET MVC's Controller has setter injection on IActionInvoker and ITempDataProvider (they have default implementations)
Model binders are also injectable.
If you're just starting out with dependency injection, IMHO the .NET framework is the worst place you can learn from: most of the time you won't have the source code, it's framework-level (not application-level) code with quite special requirements. In particular Microsoft is very careful to make things public (default is internal), as opposed to most open source projects, in order to better manage their breaking changes.