[EBookBackendGoogle] Do not store active views in its own way

Storing active views on its own has these issues:
a) it is already done in EBookBackend itself
b) referencing issues - the backend can leak without proper dereference
c) reuse EBookBackend code (not only the structure) where applicable

As a side-effect, some other memory leaks had been fixed as well.