+1, please
Using the browser analogy to justify the current workflow doesn’t stand up. Browser tabs represent a response to a request at a specific point in time. A browser tab doesn’t automatically “stay in sync” to reflect changes on the web server. So there is a compelling use case for multiple open tabs for the same URL.
What Obsidian has is an excellent start to a tab-based workflow for information management – the next evolutionary step after the original pane-based workflow. But given that these days, Obsidian tabs are primarily live views of user-editable content (as opposed to the memorialization of a historical, static web request/response), a true, 100% complete implementation does necessitate this feature/option, as well as native support for tab switching in MRU (most recently used) order.