DevForce Silverlight already uses a fault behavior and sets the includeExceptionDetailInFaults flag to true. That's why you get any exception information at all on the client, even if the information sometimes seems a bit paltry. We actually used the MSDN library article you linked for guidance when we wrote our behavior. Unless your implementation does something above and beyond that described in the article, then you won't gain anything. If you do want to use your implementation, you'll need to remove the DevForce IdeaBlade.Core.Wcf.Extensions.SilverlightFaultBehavior before adding yours.
So maybe the question is, how do we improve the exception information received on the client? The EntityServerException, which almost any server-side exception is wrapped in, may not be capturing all the inner exception information. We also have the problem that an exception received on the client can be re-thrown (sometimes more than once), so the stack trace becomes fairly unusable. Another complication is that frequently many errors manifest as "Server not found". This is frustrating, but from the client's perspective it's true - it can't communicate with the server and usually the underlying CommunicationException doesn't explain why. Any errors that occur while a response is sent to the client - usually serialization errors - also don't provide useful exception information.
Do you have any specific areas where you'd like to see better exception detail?