Is this the intended behaviour?
2014-07-03 16:31:24 askfor tx 190c3455a770ff461fc899a4c5f7e7ddc108673f984352c3e90d7b1714e1748a 0 (00:00:00) peer=29 2014-07-03 16:31:24 Requesting tx 190c3455a770ff461fc899a4c5f7e7ddc108673f984352c3e90d7b1714e1748a peer=29 2014-07-03 16:31:25 askfor tx 190c3455a770ff461fc899a4c5f7e7ddc108673f984352c3e90d7b1714e1748a 1404405803000000 (16:43:23) peer=39 2014-07-03 16:31:26 askfor tx 190c3455a770ff461fc899a4c5f7e7ddc108673f984352c3e90d7b1714e1748a 1404406043000000 (16:47:23) peer=40 2014-07-03 16:31:26 AcceptToMemoryPool: peer=29 /Satoshi:0.8.6/ : accepted 190c3455a770ff461fc899a4c5f7e7ddc108673f984352c3e90d7b1714e1748a (poolsz 793) 2014-07-03 16:45:23 Requesting tx 190c3455a770ff461fc899a4c5f7e7ddc108673f984352c3e90d7b1714e1748a peer=39 2014-07-03 16:45:23 ignoring large orphan tx (size: 15203, hash: 190c3455a770ff461fc899a4c5f7e7ddc108673f984352c3e90d7b1714e1748a) 2014-07-03 16:49:23 Requesting tx 190c3455a770ff461fc899a4c5f7e7ddc108673f984352c3e90d7b1714e1748a peer=40