It is asp.net ode behind page which is making the request to remote
object.

ASP.net will have mutple threads running to serve mutiple request from
differents clinets(Browser).

Request to the remote server for objects could be made concurrently
from different asp.net threads.

when remote server asks clients to renew the lease whould it go to
right thread.

I think it would but just wanted to confirm.

it is NOT a thick client application where clinet would be different
physical machine.

In my case it same asp.net process/same machine (multiple thread ) that
is making call.

So in short will remoting infrastructure  identify the thread that made
the call and ask that specfic tharad only to renew the lease.

Just wanted to confirm it.

2)Also won't i end up having objects longer in memory than they would
be if i was to lets say just use them locally.
because this check of lease renewal will only happen at certain
interval object will be in memory of remote server slightly longer that
required.
Would this cause any perormance issues on a high stress environment?

only counter argument i can think for this is that even when we
deallocate a object garbage collector does not collect it immediately
so if remoting adds few more second/millisecond to it it may be okay..

but again need to see what others think about it.

Thanks
Sidd