Major Description
The request scope is maintained in a Map of (key, Map) pairs where key is the scopeId and Map is the scopeMap – a Map containing all the current request attributes managed in the bridge request scope. The bridge shouldn't notify attributes in this scopeMap merely because the Map is being replaced/updated – as the bridge does this at the end of every request. (I.e. the bridge lifecyle restores the real request scope from this Map at the beginning of the request and then creates a new Map of the request scope at the end of the request which it pushes back. As this new Map really is just an updated version of the original – release notification isn't desired/shouldn't be done. But it is. So fix it.