Is a DependencyService implementation class treated as a singleton.

Are dependency services treated as singletons? I have implemented a constructor in my dependency service that only gets called once from two independent callers.

I have implemented a common interface for abstracting platform specific hardware capabilities.

My shared code that calls the dependency service is similar to the following:
DependencyService.Get().MyMethod();

Does anyone know if there are any conditions in which a DependencyService class would call its deconstructor and force the constructor to be called again when another method was invoked?