You'd previously indicated you saw this problem only when browsing to the EntityServer.svc, not when running your application, and I assume that is still the case.
I'm not seeing this problem in the upcoming 6.1.9 release, which is due this week. We did not specifically attempt to fix this problem, so it's unclear why this release seems to work while 6.1.7 (and 6.1.8, and maybe other releases) do not.
You can also check the debuglog when you navigate to either EntityService.svc or EntityServer.svc. If generated, it may indicate the problem. For example, if the license key is not found or is invalid you may see this contract error, since DevForce will not create service endpoints when a license is not found, therefore triggering the WCF simplified configuration to do so.
We have an open bug report to look into this further.