This isn't fixable without robbing Peter to pay Paul (fixing it for you and breaking it for someone else).
You would think it would be fine to resolve the symlinks when doing the matching (trivial to do). Nope. Can't do that because there are customers that have build tools which only work on the unresolved absolute name. There's no way for us to know which one is the one they really want us to use. When SlickEdit parses in the buffer name, it's always uses the unresolved absolute filename. When we've broken this, we get notified pretty quickly.
When opening a file, it isn't safe to open a file twice. If you specified the wrong path, you have to close it if you want to correct the buffer name. There's no other option for that case.