I'm not sure of the conflict, because in MVC/WebAPI optionality was _implemented_ using a default value. We removed the hack this time around.

I don't think there's any real scenario for this (optional parameter with default value), and IMO shouldn't be supported.